Automatic reverse channel assignment in a two-way TDM communication system

ABSTRACT

To minimize overhead in the allocation of channels, forward and reverse link time slots are automatically assigned in pairs. In particular, rather than requiring a separate process for allocating reverse link channels for the sending of acknowledgment messages in response to receipt of a forward link packet, a different scenario takes place. At the receiving end, such as for valid reception of data on a forward link channel at a central base station site, a reverse link time slot is automatically allocated in a time slot which depends upon the time slot allocation on the forward link. This assists with the rapid return of acknowledgment messages in a reverse link direction which is the predominant direction for such messages in a wireless system wherein most data traffic is Web page oriented.

BACKGROUND

Continued growth in the electronics and computer industries, and indeed in the economy in general, is increasingly driven by the demand for access to the Internet and the myriad of services and features that it provides. The proliferation in the use of portable computing equipment, such as laptop computers, hand-held Personal Digital Assistants (PDAs) and Internet-enabled cellular telephones have resulted in a corresponding increase in demand for wireless access to computer networks. However, at the present time, existing wireless networks, such as the cellular telephone network, are not optimum for data communications. This is at least in part due to the architecture of such networks as originally designed. In particular, these networks were intended to support voice communications, as compared to the digital communication protocols needed for Internet packet-oriented communications. For example, voice grade services typically require access to a communication channel bandwidth of approximately 3 kilohertz (kHz). While techniques do exist for communicating data over such radio channels at a rate of 9.6 kilobits per second (kbps), such low bandwidth channels do not lend themselves directly to efficient transmission of data at the typical rates of 56.6 kbps or higher that are now commonly expected using wireless modems.

In addition, the very nature of Internet traffic itself is different from the nature of voice traffic. Voice communication requires a continuous duplex connection, that is, a user at one end of a connection expects to be able to transmit and receive to a user at the other end of a connection, while at the same the user at the other end is also transmitting and receiving.

However, the usage patterns of Internet data transmission systems are quite different from voice. For example, consider that access to Web pages over the Internet in general is burst-oriented. Typically, the user of a remote client computer first specifies the address of a Web page to a browser program. The browser program at the client computer then sends the request as a Transmission Control Protocol (TCP)/Internet Protocol (IP) message packet, which is typically about 100 bytes in length, to a network Web server. The Web server then responds with the content of the requested Web page, which may include anywhere from approximately 10 kilobytes to several megabytes of text, image, audio or video data. The user may thereafter spend several seconds or even several minutes reading the contents of the page before specifying a next Web page to be downloaded.

The result is that a typical Internet connection remains idle for a relatively long period of time. However, once a request is made, the user expects the information to be transmitted to the client at a relatively rapid rate. Therefore, making available channels only on an instantaneous “as needed” basis makes sense and indeed is a requirement if wireless data transfer services are to efficiently co-exist with the existing wireless voice communication systems. Therefore, dynamic traffic channel allocation schemes are required to increase the efficiency of high performance wireless data communication systems in an effort to more efficiently utilize available channel resources.

Furthermore, in most wireless systems, there are typically many more potential users or subscribers than available radio channel resources. Therefore, some type of demand-based multiple access technique is therefore typically required to make maximum use of the available radio channels. Multiple access is often provided in the physical layer, such as by Frequency Division Multiple Access (FDMA) or by schemes that manipulate the radio frequency signal such as Time Division Multiple Access (TDMA) or Code Division Multiple Access (CDMA). In any event, the nature of the radio spectrum is such that it is a medium that is expected to be shared. This is quite dissimilar to the traditional environment for data transmission, in which a wired medium such as a telephone line or network cabling is relatively inexpensive to obtain and to keep open all the time.

SUMMARY OF THE INVENTION

A particular problem exists with efficiently adapting communication systems which use on-demand multiple access techniques in the physical layer to efficiently handle the TCP/IP message traffic which is prevalent in Internet communications. Consider that the TCP/IP protocol is a frame-based protocol requiring the acknowledgment of the receipt of message frames. Thus, for example, when a user requests that a Web page be transmitted, the initial message requesting the Web page is sent on a reverse link communication channel from a client computer towards a Web server computer. The sending of the request message also requires allocation of a forward link connection to allow the acknowledgment message to return from the server to the client.

Unfortunately, in a wireless communication environment in which demand access is granted to wireless radio channels, opening up a new reverse link channel for the acknowledgment message is a time consuming process. For example, to allocate a channel in the reverse link direction may indeed end up taking longer than the time necessary to simply transmit the very short acknowledgment message.

The present invention seeks to overcome these difficulties. The invention is used in a time division multiplex (TDM) communication system supporting duplex operations whereby multiple users share forward and reverse channels. The system makes use of time slots to allocate specific channels on a demand basis. Thus, for example, a given forward link channel is allocated for only a predetermined time slot duration and only upon user request.

To minimize overhead in the allocation of channels, forward and reverse link time slots are automatically assigned in pairs. In particular, rather than requiring a separate process for allocating reverse link channels for the sending of acknowledgment messages in response to receipt of a forward link packet, a different scenario takes place. At the receiving end, such as for valid reception of data on a forward link channel at a central base station site, a reverse link time slot is automatically allocated in a time slot which depends upon the time slot allocation on the forward link.

This scheme assists with the rapid return of acknowledgment messages in a reverse link direction which is the predominant direction for such messages in a wireless system wherein most data traffic is Web page oriented.

The invention has several other advantages. Among these include the avoidance of the need to set up and tear down channels, especially reverse link channels, for the limited purpose of sending acknowledgment messages.

Minimizing the amount of reverse link traffic on shared frequency channels, such as in a CDMA system, in turn increases the data handling capacity of the entire system. The reverse link messages may also include other types of anticipated short messages, depending upon the type of forward link messages sent. For example, these may include link layer acknowledgment messages, or higher layer GET messages for links embedded in a Web page.

While the invention provides particular advantages in not explicitly allocating reverse link traffic channels for the anticipation of acknowledgment and other short messages, dedicated reverse link channels may still be explicitly allocated for long message traffic.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.

FIG. 1 is a block diagram of a communication system in which reverse channel assignment occurs automatically in response to valid reception of data on a forward link channel.

FIG. 2 is a diagram depicting channel slot assignments.

FIG. 3 is a message sequence chart illustrating a typical message sent on the reverse link and the resulting acknowledgment sent on the forward link.

FIG. 4 is a message sequence chart illustrating a typical forward link message and resulting acknowledgment message to sequence on the reverse link.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

FIG. 1 is a block diagram of a communication system 10 that is suitable for automatic assignment of a reverse link channel such as to carry acknowledgment messages in response to a receipt of a valid message on a forward link channel. In particular, the communication system 10 shown includes a number of personal computer (PC) devices 12-1, 12-2, . . . 12-h, . . . 12-l, and corresponding Subscriber Access Units (SAUs) 14-1, 14-2, . . . 14-h, . . . 14-l, and associated antennas 16-1, 16-2, . . . 16-h, . . . 16-l. Centrally located equipment includes a base station antenna 18, a base station processor (BSP) 20, Internet gateway 22, Internet 24, and network file server 30. The system is a demand access, point to multi-point wireless communication system such that the PCs 12 may transmit data to and receive data from network server 30 through wireless connections implemented over forward links 40 and reverse links 50. It should be understood that in a point to multi-point multiple access wireless communication system 10 as shown, a given base station processor 20 typically supports communication with a number of different subscriber access units 14 in a manner which is similar to that used in a cellular telephone communication network.

The PCs 12 may, for example, be laptop computers 12-l, handheld 12-h, or Personal Digital Assistant (PDA)-type computers. The computers 12 are each connected to a respective SAU 14 through a suitable wired connection such as an Ethernet-type connection. The respective SAU 14 permits the PC 12 to be connected to the network file server 30 through several types of physical connections.

In the reverse link direction, that is, for data traffic traveling from the PC 12 towards the server 30, the PC 12 provides an Internet Protocol (IP) level packet to the SAU 14 over the wired connection. The SAU 14 then appends to the wired framing (i.e., Ethernet framing) in the IP packet and inserts appropriate wireless connection framing. The appropriately formatted wireless data packet then travels over one or more radio channels provided by the reverse link 50 through the antennas 16 and 18. At the central base station, the BSP 20 extracts the radio link framing, reformatting the packet in IP form and routes it through the Internet gateway 22. The packet is then forwarded through any number and/or type of TCP/IP networks, such as the Internet 24, to its ultimate destination, such as the network file server 30.

By way of example, the wireless packet framing information may be that described in Patent Cooperation Treaty Application No. WO99/44341 entitled “Dynamic Frame Size Setting For Multichannel Transmission,” published Sep. 2, 1999, and which is hereby incorporated by reference. In that scheme, Code Division Multiple Access (CDMA) encoding is used to define multiple logical channels on a given physical channel. For example, a long pseudo-random noise (PN) code sequence can be used to define multiple logical channels on a given radio frequency carrier signal. Other codes may be layered on the long PN code, such as error correction codes or optional short pseudo-random noise (PN) codes, to further define the channels and make them robust in noisy environments.

Data may also be transmitted in the opposite direction, that is, from the network file server 30 to the PCs 12, in a forward direction. In this instance, an Internet Protocol (IP) packet originating at the file server 30 travels through the Internet 24 through the Internet gateway 22 arriving at the BSP 20. Appropriate wireless protocol framing is then added to the IP packet. The packet then travels through the antenna 18 and 16 to the intended receiver SAU 14. The receiving SAU 14 then processes the message according to the wireless packet formatting, ultimately forwards the packet to the intended PC 12 which performs the IP layer processing. A given SAU 14 and the file server 30 are thus viewed as the end points of a given duplex connection at the IP level. Once a connection is established, a user at the PC 12 may therefore transmit data to and receive data from the file server 30.

In accordance with the link layer or even a higher layer TCP/IP protocol, a receiving endpoint is expected to send an acknowledgment message to the corresponding sending unit upon complete and correct receipt of a packet. This acknowledgment message may be sent in response in a cumulative fashion, such that a given acknowledgment message indicates that a number of consecutive packets have been received successfully. However, in any event, it can be appreciated that these acknowledgment messages in the system 10 must be sent over the forward link 40 or reverse link 50 in response to messages sent on the reverse 50 or forward 40 link, respectively. Given that the system 10 is a wireless system, radio resources must therefore be provisioned for sending such acknowledgment messages regardless of the exact physical layer configuration.

As will be described in greater detail later, the reverse link 50 actually consists of a number of different types of logical and/or physical radio channels including an access channel 51, multiple traffic channels 52-1, . . . 52-t, and a maintenance channel 53. The reverse link access channel 51 is used by the SAUs 40 to send messages to request that traffic channels be granted to them. The assigned traffic channels 52 then carry payload data from the SAU 14 to the BSP 20. It should be understood that a given IP level connection may actually have more than one traffic channel 52 assigned to it as described in the previously referenced patent application. In addition, a maintenance channel 53 may carry information such as synchronization and power control messages to further support transmission of information over the reverse link 50.

Similarly, the forward link 40 typically includes a logical paging channel 41 that is used by the BSP 20 to not only inform the SAU 14 that forward link traffic channels 52 have been allocated to it, but also to inform the SAU 14 of allocated traffic channels 52 in the reverse link direction. Traffic channels 42-1 . . . 42-t on the forward link 40 are used to carry payload information from the BSP 20 to the SAUs 14. Additionally, maintenance channels carry synchronization and power control information on the forward link 40 from the base station processor 20 to the SAUs 14.

Additional information as to one possible way to implement the various logical channels 41, 42, 43, 51, 52, and 53 is also provided in Patent Cooperation Treaty Application No. WO99/63682 entitled “Fast Acquisition Of Traffic Channels For A Highly Variable Data Rate,” published Dec. 9, 1999.

As shown more particularly in FIG. 2, a typical forward link traffic channel 42 is partitioned into a pre-determined number of periodically repeating time slots 60-1, 60-2, . . . 60-n for transmission of messages to the multiple SAUs 14. A given SAU 14 identifies messages directed to itself based upon when a message is received in an assigned time slot 60. It should be understood that a given SAU 14 may at any instant in time have multiple ones of the time slots 60 assigned to it or at other times may have no time slots assigned to it. The assignment of time slots 60 is communicated from a central controller such as a wireless Internet facility base station controller 23 or the BSP 20 itself over the paging channel 41. The allocation of radio and traffic channels occurs on a demand basis among the various SAUs 14 in a physical area serviced by the system 10.

The manner of assignment of the time slots and radio channels is not of importance to the present invention; rather the present invention is more concerned with the manner in which a time slot 60 is automatically assigned in the reverse link 50 upon reception of a valid message on the forward link 40.

In particular, the reverse link traffic channels 52 are shared among the multiple SAUs 14. For example, a given reverse link traffic channel 52-i is partitioned into a number of time slots 70-1 . . . 70-n in a manner similar to the way in which the forward link traffic channel 42-i is partitioned.

Consider that a given forward link traffic channel 42-i may include a particular time slot 60-4. This time slot 60-4 carries packet data from the base station processor 20 to an intended SAU 14-2. However, unlike prior art systems, there is no specific assignment needed of reverse link traffic channel slots by sending paging channel messages to inform the connection associated with the particular time slot 60-4. Rather, upon receiving the data packet in time slot 60-4, the SAU 14 determines whether the data has been properly received such as by performing error check processing. If the packet is indicated as having been received properly, the SAU 14 makes an assumption that the acknowledgment message will be expected to be transmitted in corresponding time slot 70-4 on the reverse link traffic channel 52-i.

The time slot 70-4 is positioned timewise a given number of time slots, m, away from the time slot 60-4 allocated to the forward link. This, in effect, results in automatic reservation of a reverse link time slot for the acknowledgment message a fixed number of time slots, m, in the future.

Similarly, an acknowledgment message for a packet sent in time slot 60-2 is acknowledged in the time slot 70-2. The time slot 70-2 remains the m time slots away from its associated forward link time slot 60-2.

Several advantages result from this arrangement. In particular, no control signaling is required on the paging channel 41 to allocate reverse link time slots for the acknowledgment messages. The technique efficiently uses the reverse channel for acknowledgment messages such as TCP/IP layer ARQ messages among a large number of SAUs 14. The short time delay duration for these acknowledgment messages in turn increases the effective utilization of the traffic channels 52 on the reverse link, as well as the paging channel 41 on the forward link 40.

It should be understood that the time slot 70-4 can also carry other short messages, such as link layer acknowledgment messages. In many applications, link layer acknowledgments must be handled rapidly, and the invention provides this capability.

At higher protocol levels, the reverse time slot can be used for sending embedded links in a Web page. For example, a typical Hypertext Transfer Protocol (HTTP) Web page file has several embedded links which are requests to fetch other files. These embedded links can be sent back on the reverse channel using the time slots 70-4.

FIG. 3 depicts a message sequence chart illustrating the transmission of a TCP/IP packet and acknowledgment message exchange traveling in the reverse direction, that is from the PC 12 towards the server 30, with the server 30 sending the acknowledgment message back to the PC12. The protocol diagram indicates message flow from right to left through the PC 12, SAU 14, BSP 20 and Web file server 30. The protocol diagram depicted in FIG. 3 is typical for the transmission of messages in a worldwide Web type environment.

This exchange of messages is typical of prior art systems in that a channel is explicitly allocated for acknowledgment in the message transmission. For example, the user of the PC 12 may be specifying a Web page address for which it is desired to be downloaded from the file server 30 to the PC 12. The message thus typically consists of a higher level protocol (Hypertext Transfer Protocl ((HTTP), File Transfer Protocol (FTP), or the like) page request or “GET” message which is layered on the TCP/IP protocol. In any event, a first message consists of a TCP/IP layer message that contains a data packet indicated in the diagram as packet (A).

Next, the SAU 14 receives this TCP/IP layer data message 301 and reformats it for transmission over the wireless reverse link 50. In particular, the receipt of the TCP/IP message (A) results in a number of messages being sent on the access channel 51, paging channel 41, and traffic channels 52.

First, a message 302 is sent on the access channel 51 requesting the allocation of traffic channels 52 from the BSP 20. This message 302 typically consists of identification information that identifies the particular SAU 14 requesting the traffic channels, and a command, such as OPEN, that indicates to the BSP 20 that the associated SAU 14 is requesting that a logical traffic channel be opened.

In response thereto, the BSP 20 sends a channel allocation message on the forward link paging channel 41. This channel allocation message 304 indicates an SAU identification (ID), and a pseudo-random noise code assigned for the traffic channel and to permit the SAU 14 to decode its respective logical channel, and information indicating one or more of time slots to which this connection is being allocated.

In response to receipt of message 304, the payload portion of the packet (A) is then partitioned by the SAU 14 among the available allocated time slots. Thus, it may actually be necessary to transmit the packet (A) in multiple segments indicated as SEG 1, SEG 2, . . . SEG p in multiple traffic messages 306, 308, . . . , 312 sent on the traffic channels 52. It should be understood that depending on system loading requirements and capacity, a given connection may be allocated a single time slot on a single reverse link traffic channel 52, or it may be the situation where multiple traffic channels and/or time slots may be allocated to transmission of the various segments of packet (A).

In any event, the BSP 20 receives the messages 306, 308, . . . , 312 containing the various segments SEG 1, SEG 2, . . . SEG p and reassembles them into the complete TCP/IP data packet (A). The assembled packet (A) is then reformulated as a TCP/IP message 314 and forwarded to the Web file server 30.

If Web file server 30 receives packet (A) correctly, it then provides an acknowledgment message 316 intended for the PC 12 that originated the message. To send this acknowledgment message thus requires the allocation of a radio channel to forward it to the respective SAU 14. This channel allocation process involves first sending a message 317 on the forward paging channel 41 indicating to the respective SAU to allocate a code channel and time slot for the acknowledgment message.

A message 318 is then sent on the indicated traffic channel with the appropriate code and assigned time slot for the acknowledgment 318. Upon receipt of message 318 at the SAU 14, the acknowledgment message is reformulated as a TCP/IP level frame in message 320 and forwarded to the PC 12. Further messages are then needed to deallocate the forward link traffic channel 40 allocated for the acknowledgment message by, for example, sending a message 322 on the access channel requesting that the traffic channel be closed, and acknowledgment of the closing of the message being returned on the paging channel by message 324.

Turning attention now to FIG. 4, it can be understood how messages are exchanged for acknowledgment on the forward link 40 without the need to explicitly allocate channels for acknowledgment messages on the reverse link 50. FIG. 4 depicts the message sequence for a packet (B) traveling in a forward link 40 direction from the Web server 30 towards the PC 12. It will be understood in this situation that these packets typically include Web page data being transmitted down to the PC 12 from the Web file server 30, and thus are typically transmitted far more often than messages traveling in the reverse link 50 direction. Thus, these forward link messages, being far more common and prevalent, benefit greatly from a more efficient acknowledgment scheme.

In any event, the data packet (B) originates as a TCP/IP level message 400 at the Web server 30 and is then forwarded to the BSP 20. Upon receipt of this message 400, the BSP 20 then causes a number of messages 412, 414, 416 and 418 to be exchanged between the BSP 20 and SAU 14. In particular, a paging channel message 412 is sent on the forward link 40 indicating an SAU ID, PN code, and one or more time slots being assigned between the BSP 20 and the particular SAU 14. This message is then acknowledged, for the wireless physical layer connection, by a return message 414 being sent from the SAU 14 back to the BSP 20. This indicates to the BSP 20 that the SAU 14 is ready to receive data.

The BSP 20 then proceeds to send the various segments SEG. 1, SEG. 2, . . . SEG. s as a series of messages 416, 417, 418 sent on one or more of the forward traffic channels 42 at indicated slots and with indicated codes. Upon completion of these messages, SAU 14 has received all of the segments making up the packet (B). These segments may then be reformulated as a TCP/IP layer data packet (B) in a message 420 which is forwarded to the PC 12.

The PC 12 then returns an acknowledgment message 422 to the SAU 14. This in turn causes a single message 424 to be sent on a traffic channel on the reverse link 50. The time slot for this message is determined from the time slotss allocated on the forward link to the same connection. (This has been described previously in connection with FIG. 2.) The acknowledgment message is received at the BSP 20 and then reformulated as a TCP/IP layer acknowledgment packet 430 and forwarded to the Web server 30.

While this invention has been particularly shown and described with references to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims. 

What is claimed is:
 1. A method for communication in a time division multiple access system where access to physical layer channels is assigned on a time slot basis, the method comprising: allocating at least one time slot to carry forward link messages on a forward link logical channel; sending at least one forward link packet in a forward link direction using one or more of the allocated time slots; upon receipt of a valid complete forward link packet: allocating at least one time slot on a reverse link logical channel to carry a short message related to the forward link packet, the time slot on the reverse link being located a predetermined time spacing away from one of the time slots allocated on the forward link for the same connection, thereby eliminating the need to send specific time slot allocation messages for the short message on the reverse link.
 2. A method as in claim 1 wherein the system is a wireless communication system.
 3. A method as in claim 1 wherein the short message is a link layer acknowledgment message for the forward link packet.
 4. A method as in claim 1 wherein the short message is a TCP/IP layer acknowledgment message for the forward link packet.
 5. A method as in claim 1 wherein the short message is an HTTP layer embedded link request.
 6. A method as in claim 1 wherein the forward link packet is a network layer packet.
 7. An apparatus for communicating in a Time Division Multiple Access (TDMA) system comprising: a central controller allocating at least one time slot to carry forward link messages on a forward link logical channel; a sending unit in electrical communication with the central controller, the sending unit configured to send at least one forward link packet in a forward link direction using one or more of the allocated time slots; a receiving end point in electrical communication with the sending unit and the central controller, the receiving end point, upon receipt of a valid complete forward link packet, allocating at least one time slot on a reverse link logical channel to carry a short message related to the forward link packet, the time slot on the reverse link being located a predetermined time spacing away from one of the time slots allocated on the forward link for the same connection, thereby eliminating the need to send specific time slot allocation messages for the short message on the reverse link.
 8. The apparatus of claim 7, wherein the TDMA system comprises a wireless communication system, the receiving end point being in wireless, electrical communication with the sending unit.
 9. The apparatus of claim 8, wherein the central controller comprises a wireless interface processor.
 10. The apparatus of claim 8, wherein the central controller comprises a base station processor.
 11. The apparatus of claim 8, wherein the sending unit comprises a base station processor.
 12. The apparatus of claim 8, wherein the receiving end point comprises a subscriber access unit.
 13. The apparatus of claim 7, wherein the short message is a link layer acknowledgment message for the forward link packet.
 14. The apparatus of claim 7, wherein the short message is a TCP/IP layer acknowledgment message for the forward link packet.
 15. The apparatus of claim 7, wherein the short message is an HTTP layer embedded link request.
 16. The apparatus of claim 7, wherein the forward link packet is a network layer packet.
 17. An apparatus for communicating in a Time Division Multiple Access (TDMA) system where access to physical layer channels is assigned on a time slot basis, comprising: means for allocating at least one time slot to carry forward link messages on a forward link logical channel; means for sending at least one forward link packet in a forward link direction using one or more of the allocated time slots; upon receipt of a valid complete forward link packet: means for allocating at least one time slot on a reverse link logical channel to carry a short message related to the forward link packet, the time slot on the reverse link being located a predetermined time spacing away from one of the time slots allocated on the forward link for the same connection, thereby eliminating the need to send specific time slot allocation messages for the short message on the reverse link. 